Google ADK Agents Instrumentation#1767
Conversation
TimPansino
force-pushed
the
feat-google-adk-agent-instrumentation
branch
from
facf5dc to
378260f
Compare
✅MegaLinter analysis: Success
Notices📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining See detailed reports in MegaLinter artifacts
|
TimPansino
force-pushed
the
feat-google-adk-agent-instrumentation
branch
from
75fd23d to
e9f0722
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop-google-adk #1767 +/- ##
=====================================================
Coverage ? 81.65%
=====================================================
Files ? 216
Lines ? 26511
Branches ? 4180
=====================================================
Hits ? 21647
Misses ? 3453
Partials ? 1411 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
| func_name = callable_name(wrapped) | ||
| agent_name = getattr(instance, "name", "agent") | ||
| function_trace_name = f"{func_name}/{agent_name}" | ||
| agentic_subcomponent_data = {"type": "APM-AI_AGENT", "name": agent_name} |
There was a problem hiding this comment.
Going forward, we will ideally only want to send the subcomponent attr if we have a local agent executing (rather than an invocation by a local or remote agent). Is there a way in the ADK repo to distinguish between remote and local agents and executions vs invocations?
There was a problem hiding this comment.
Remote agents are handled by a separate class entirely, and it looks like there's a parent_agent field on all agents that can determine if this is a sub agent and not a top level agent.
mergify
Bot
added
tests-failing
|
Tick the box to add this pull request to the merge queue (same as
|
3 participants
Overview